Feature/installtion instructions.md #160
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Installations.md
Outdated
| @@ -7,7 +7,7 @@ | |||
| # For Windows | |||
| The first step is to install the ESP-IDF v4.2. | |||
There was a problem hiding this comment.
Done, am commiting the changes now
* Changed the odd instance of v4.2 to v5.2 * Updated the installation instructions for MacOS
Removed an incorrect line from a previous commit
Shankari02
reviewed
Feb 5, 2025
| </p> | ||
|
|
||
| ### Step 7: Open ESP-IDF 4.2 CMD which should be on your desktop | ||
| ### Step 7: Open ESP-IDF 5.2 PowerShell which should be on your desktop |
There was a problem hiding this comment.
@JaytidaA you haven't updated your fork before pushing these changes. This has caused the same changes to appear which have been done previously which might result in merge conflicts
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Further work for resolving Issue #148